System agnostic front end application for legacy systems

ABSTRACT

A system and method for accessing data in one of a first legacy computer system that has a first operating system and a second legacy computer system that has a second operating system that is different from the first operating system. The method includes providing a front end application that is in communication with the first and second legacy computer systems, with the application being displayed on a user interface of a computer. Aircraft and maintenance data of a first legacy airline is associated with the first legacy computer system and aircraft and maintenance data of a second legacy airline is associated with the second legacy computer system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a division of U.S. application Ser. No. 15/337,473,filed Oct. 28, 2016, which claims the benefit of the filing date of, andpriority to, U.S. Application No. 62/248,427, filed Oct. 30, 2015, theentire disclosures of which are hereby incorporated herein by reference.

BACKGROUND

When two airlines and their aircraft fleets and maintenance crews merge,mechanics are required to service aircraft from each of the two fleets.Generally, data associated with one of the airlines is stored in a firstlegacy computer system and data associated with another airline isstored in a second legacy computer system. At some point, a mechanicthat is familiar with the first legacy computer system must service anaircraft having data stored in the second legacy computer system.Assuming the first and second legacy systems are different, the mechanicmust learn, understand, and use different commands, data inputs,parameters, and formatting for each of the first and second legacysystems. Similarly, training and qualification data for each mechanicwithin the two airlines is stored in either the first or second legacycomputer systems. Thus, in order to evaluate whether a mechanicassociated with the first legacy computer system is qualified tocomplete a maintenance task associated with an aircraft having datastored in the second legacy computer system, two different legacycomputer systems must be accessed. This may result in increased risk ofnon-compliance.

Therefore, what is needed is a system, method, or apparatus thataddresses one or more of the foregoing issues, among others.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic illustration of a system, according to anexemplary embodiment.

FIG. 2 is a conceptual architecture view of the system of FIG. 1,according to an exemplary embodiment.

FIG. 3 is a data architecture view of the system of FIG. 1, according toan exemplary embodiment.

FIG. 4 is a logical architecture view diagram of the system of FIG. 1,according to an exemplary embodiment.

FIG. 5 is a flow chart illustration of a method implemented in whole orin part using the system of FIG. 1, according to an exemplaryembodiment.

FIGS. 6A-6E are flow chart illustrations of a process flow of the systemof FIG. 1, according to an exemplary embodiment.

FIGS. 7A-7C are configuration views of the system of FIG. 1, accordingto an exemplary embodiment.

FIG. 8A-8C are flow chart illustrations of yet another process flow ofthe system of FIG. 1, according to an exemplary embodiment.

FIG. 9 is a diagrammatic illustration of a node for implementing one ormore exemplary embodiments of the present disclosure, according to anexemplary embodiment.

DETAILED DESCRIPTION

The following disclosure provides many different embodiments orexamples. Specific examples of components and arrangements are describedbelow to simplify the present disclosure. These are, of course, merelyexamples and are not intended to be limiting. In addition, the presentdisclosure may repeat reference numerals and/or letters in the variousexamples. This repetition is for the purpose of simplicity and clarityand does not in itself dictate a relationship between the variousembodiments and/or configurations discussed.

In an exemplary embodiment, as illustrated in FIG. 1, a system generallyreferred to by the reference numeral 10 includes a System Agnostic FrontEnd (“SAFE”) application 15, which provides a common “front end”application that is in communication with both a first legacy computersystem 20 (e.g., legacy system of American Airlines) of a first legacyairline (e.g., American Airlines) and a second legacy computer system 25(e.g., legacy system of US Airways) of a second legacy airline (e.g., USAirways) to ensure regulatory compliance and to accelerate adoption of asingle process, such as a single maintenance process. Generally, a“front end” application is an application that a user, using a computer30 that includes a graphical user interface 30 a, interacts withdirectly via a network 35. Generally, the SAFE application 15 is aweb-based application that is accessed on the computer 30 using a webbrowser. In an exemplary embodiment, the SAFE application 15 isgenerally a multi-tier application such that presentation, applicationprocessing, and data management functions are physically separated.

In an exemplary embodiment, the first legacy computer system 20 includesan operating system that is different from an operating system of thesecond legacy computer system 25. In an exemplary embodiment, the firstlegacy computer system 20 and the second legacy computer system 25 havedifferences in data schema. The operating system of the first legacycomputer system 20 is a Semi-Automatic Business Research Environment(“SABRE”) system. In an exemplary embodiment, the operating system ofthe second legacy computer system 25 is a System Computerized forEconomical Performance, Tracking, Recording, and Evaluation (“SCEPTRE”)system. A command to perform an action in the operating system for thefirst legacy computer system 20 is generally different from, or not thesame as, a command to perform the same action in the operating systemfor the second legacy computer system 25. Additionally, the first legacycomputer system 20 is a non-web based system so that accessing the firstlegacy computer system 20 requires access to specific hardware on whichthe first legacy computer system 20 is installed. Similarly and in anexemplary embodiment, the second legacy computer system 25 is a non-webbased system so that accessing the second legacy computer system 25requires access to specific hardware on which the second legacy computersystem 25 is installed. Thus, to execute a generic command, such as tosearch for data relating to an aircraft or to create a logbook entryassociated with the aircraft on which a user is working, the user mustdetermine whether data associated with the aircraft is associated withthe first legacy computer system 20 or the second legacy computer system25. After determining which legacy computer system is associated withthe aircraft, the user must access the specific hardware on which eitherthe first legacy computer system 20 or the second legacy computer system25 is installed. After which, the user must enter commands that arespecific to either the first legacy computer system 20 or the secondlegacy computer system 25 in order to search for data relating to theaircraft and/or to create the logbook entry associated with theaircraft. In response to the user's request to search for data relatingto the aircraft or to create the logbook entry, maintenance history forthe aircraft may be viewed on a graphical user interface of the specifichardware that the user is accessing. This requires that the user haveaccess to specific hardware on which both the first legacy computersystem 20 and the second legacy computer system 25 are installed and befamiliar with the specific commands associated with each of the firstlegacy computer system 20 and the second legacy computer system 25.Considering at least some of the inputs and management of data for thefirst legacy computer system 20 and the second legacy computer system 25are not the same, errors can occur when having to switch between thelegacy computer systems 20 and 25. The user may also inadvertentlyfollow an incorrect procedure associated with one legacy computer systemwhen needing to follow another procedure associated with the other ofthe legacy computer systems. Also, this allows for little to no inputvalidation and error handling for inputs received via the hardware onwhich either the first legacy computer system 20 or the second legacycomputer system 25 is installed. Moreover, training and qualificationdata for a mechanic or employee of the first legacy airline is stored inthe first legacy computer system 20 while the training and qualificationdata for a mechanic or employee of the second legacy airline is storedin the second legacy computer system 25. Thus, in order to evaluatewhether a mechanic associated with the first legacy airline is qualifiedto complete a maintenance task associated with an aircraft having datastored in the second legacy computer system 25, the qualification datafor the mechanic must be accessed in the first legacy computer system 20while other data pertaining to the aircraft must be accessed in thesecond legacy computer system 25. This may result in increased risk ofnon-compliance related to mechanics being assigned to work that he orshe is not currently qualified to do. In this case and when a mechanicis not authorized or qualified to perform a task, the user or mechanicis considered an unauthorized user or mechanic to complete the task.Moreover, there is an increased risk of non-compliance due to a mechanicmaintaining an aircraft associated with the first legacy airline usingmaintenance procedures from the second legacy airline.

In an exemplary embodiment and as illustrated in FIG. 2, the SAFEapplication 15 is configured to access, update, or produce data to beused in a Web Analytics application 40 and/or an Application PerformanceMonitor application 45. The SAFE application 15 is also configured toaccess, update, or produce data such as logbook data 50, employee data55, aircraft attributes data 60, and training qualification data 65.Additionally, the SAFE application 15 may include a SAFE presentation 15a and an admin console 15 b that together create a Role andQualification Access Control application. The user, or an aircraftmechanic technician (“AMT”), may interact with the SAFE presentation 15a in that the SAFE presentation 15 a is displayed on the user interface30 a of the computer 30. In an exemplary embodiment, a businessadministration group or other designated user or group of designatedusers can manage user and user role data for users of the system 10 andmanage, alter, and edit the aircraft data via the admin console 15 b.Moreover, the business administration group or other group of designatedusers may be provided data regarding the system 10 using the WebAnalytics application 40. An Information Technology (“IT”) group ofusers can monitor application performance of the SAFE application 15 viathe Application Performance Monitor application 45.

In an exemplary embodiment, and as illustrated in FIG. 3, FlightOperating Systems (“FOS”) 20 a for first legacy computer system 20 and aFOS 25 a for the second legacy computer system 25 provide data to anequipment service system 70, which, in turn provides at least a portionof the aircraft attributes data 60 to the SAFE application 15.Generally, the aircraft attributes data 60 includes a nose number, afleet type, a registration, a carrier, etc. of an aircraft. The FOS 20 aand FOS 25 a also provide data to a Flight Information system 75, which,in turn provides flight information and flight following (“FLIFO”) datato the SAFE application 15. The FOS 20 a and a LogbookService/Orchestration system 80 also exchange data. The LogbookService/Orchestration system 80 also exchanges, with the SAFEapplication 15, data such as at least a portion of the logbook data 50.A SCEPTRE system 85 provides data to the FOS 25 a. Data is exchangedbetween the SCEPTRE system 85 and both the Logbook Service/Orchestrationsystem 80 and an Aircraft Attributes system 90. The Aircraft Attributessystem 90 provides at least a portion of the aircraft attributes data 60to the SAFE application 15. Moreover, the Aircraft Attributes system 90and a SQL Server 95 exchange data. The SQL Server 95 also exchanges datawith an Authorization Service system 100 and a Qualifications ServiceSystem 105. For example, the SQL Server 95 may exchange task andqualifications mapping data with the Qualifications Service System 105.Additionally, the SQL server 95 may manage data for any one or more ofthe following: aircraft attributes that are not available in the firstlegacy computer system 20 and the second legacy computer system 25;qualifications required to perform defined tasks; and role managementfor authorization. In an exemplary embodiment, the Qualification ServiceSystem 105 may provide additional logic such as task-to-qualificationmapping and adding filters based on locations. The Authorization servicesystem 100 also exchanges role data with the SAFE application 15. Both aLearning Path system 110 and a SABA system 115 provide data, such asqualification data pertaining to mechanics or other users, to theQualification Service system 105, which, in turn provides Qualificationdata to the SAFE application 15. In some exemplary embodiments, the SABAsystem 115 forms a portion of the first legacy computer system 20 andthe Learning Path system 110 forms a portion of the second legacycomputer system 25. The SAFE application 15 provides at least a portionof the employee data 55 to an AD system 120. For example, the employeedata may include employee identification number (“EID”) of an employee,the cost center associated with that employee, and a station/branchassociated with that employee. In an exemplary embodiment, the SAFEapplication 15 exchanges data with the AMT, which, in turn exchangesdata with an Oil Service system 125. In an exemplary embodiment, theSAFE application 15 provides links to the Oil Servicing system 125 andcarrier-specific manuals. In an exemplary embodiment, oil servicing datais a link to the aircraft Oil Servicing system 125. However, the SAFEapplication 15 may exchange data directly with the Oil Servicing system125 without interaction from the AMT. That is, the system 10 may makecalls directly to the Oil Servicing system 125 to retrieve data ratherthan deep linking to the Oil Servicing system 125. In an exemplaryembodiment, the SAFE application 15 provides links to carrier specificsystems, provides at least a portion of the aircraft attributes data 60,and at least a portion of the logbook data 50 to the AMT. As such, theSAFE application 15 allows for the AMT to edit, input, or view datastored within or associated with the FOS 20 a and the FOS 25 a. The SAFEapplication 15 may also provide a mechanism for other applications todeep link into the SAFE application 15 by providing aircraftinformation, such as nose number and carrier. The SAFE application 15may provide users with a view of aircraft history and attributes to helpensure compliance with a maintenance program prior to receiving a singleoperating certificate. In an exemplary embodiment and after receiving asingle operating certificate, the SAFE application 15 includes a webpagethat provides fast access for common AMT activities.

FIG. 4 is a logical view diagram of one exemplary embodiment of thesystem 10 that includes a consumer layer, a security layer, anapplication layer, an integration layer including an Enterprise ServiceBus (“ESB”) 130, and a resource layer. In an exemplary embodiment, thepresentation layer of the SAFE application 15 includes AngularJS and/orJQuery. In an exemplary embodiment, the application layer of the SAFEapplication 15 includes Web API and MVC, such as Razor. Generally, aLDAP 135, the Authorization service system 100, the Aircraft Attributessystem 90, the SQL Server 95, the Qualification Service system 105, theLearning Path system 110, the SABA system 115, the equipment servicesystem 70, the flight Information system 75, the FOS 20 a, the FOS 25 a,the Logbook Service/Orchestration system 80, the SCEPTRE system 85, a GTSoftware Ivory Suite 140, and a SCEPTRE Web service 145 is included inthe resource layer and generally communicate with the application layervia the ESB 130.

In an exemplary embodiment, as illustrated in FIG. 5 with continuingreference to FIGS. 1-4 and FIGS. 6A-6E, a method of accessing data inone of the first legacy computer system 20 and the second legacycomputer system 25 is generally referred to by the reference numeral150. In an exemplary embodiment, the method 150 includes providing acommon front end application, such as the SAFE application 15, that isin communication with the first legacy computer system 20 and the secondlegacy computer system 25 at step 155; receiving inputs, including ageneric command, using the SAFE application 15 at step 160; determining,based on the inputs, if data relating to the inputs is associated withthe first legacy computer system 20 or the second legacy computer system25 at step 165; if the data relating to the inputs is associated withthe first legacy computer system 20, then transforming the genericcommand to a first operating system command at step 170; if the datarelating to the inputs is associated with the second legacy computersystem 25, then transforming the generic command to a second operatingsystem command at step 175; after the step 170, the method 150 furtherincludes executing the first operating system command at step 180; afterthe step 175, the method further includes executing the second operatingsystem command at step 190; and after either the step 180 or the step185, the method 150 includes displaying at least a portion of the datarelated to the inputs using the SAFE application 15 at step 190.

At the step 155, the SAFE application 15 is provided such that the SAFEapplication 15 is in communication with the first legacy computer system20 and the second legacy computer system 25. Because the SAFEapplication 15 is a web-based application that is in communication with,and configured to access, the first legacy computer system 20 and thesecond legacy computer system 25, a user of the SAFE application 15 iscapable of accessing the first legacy computer system 20 and the secondlegacy computer system 25 using a web browser. This prevents the userfrom having to find and access hardware on which either the first legacycomputer system 20 and/or the second legacy computer system 25 isinstalled.

At the step 160, inputs are received using the SAFE application 15. Theinputs are generally received in response to the user interface 30 adisplaying a webpage that receives inputs. Generally, the inputs includea generic command that is generic to the first legacy computer system 20and the second legacy computer system 25; an aircraft identifier such asa nose number; and an employee identifier, such as an employee number oruser number. In an exemplary embodiment, the submission or entering ofthe aircraft identifier and/or the employee identifier automaticallygenerates a generic query command. Thus, the generic command of “query”is automatically “received” by the SAFE application 15 upon the entry ofthe aircraft identifier or the employee identifier. An example of ageneric command is to search for, or query, or identify data relating toan aircraft. In another exemplary embodiment, and in the event that twoseparate aircrafts are associated with the same nose number, the user isrequired to validate the fleet type of the aircraft by providing aninput regarding the fleet type of the aircraft. The inputs may alsoinclude a flight number, a date, an ARM or FMR code, etc. As illustratedin FIG. 6A, the user may be directed to a home webpage of a SAFEwebpage. The SAFE webpage and/or a web application program interface(“API”) 195 may receive the nose number, search for the nose number, andvalidate the nose number. In an exemplary embodiment, the system 10requests an identifier of an aircraft, such as a nose number from theuser and then routes the user to a webpage that displays links for theuser, such as a mechanic, for the various mechanic activities based onthe carrier. In another exemplary embodiment and in the event that twoseparate aircrafts are associated with the same nose number, the user isrequired to validate the fleet type of the aircraft. Generally, a JSONobject is generated using at least one of the inputs and then sent tothe API 195. After receiving the JSON object, the API 195 then generatesa first SOAP message 200 (shown in FIG. 6B), based on the JSON objectthat was generated using at least one of the inputs. In some exemplaryembodiments, the first SOAP message 200 includes a header that is usedto route the first SOAP message using a router 205, as illustrated inFIG. 6B. In an exemplary embodiment, the header of the first SOAPmessage 200 includes a first legacy computer system identifier or asecond legacy computer system identifier. In an exemplary embodiment, atleast one of the inputs is the first legacy computer system identifieror the second legacy computer system identifier.

At the step 165, it is determined, based on the inputs, if the datarelating to the inputs is associated with the first legacy computersystem 20 or the second legacy computer system 25. In an exemplaryembodiment, the router 205 is remote from the computer 30 and determineswhether the data relating to the inputs is associated with the firstlegacy computer system 20 or the second legacy computer system 25. In anexemplary embodiment, the determination is based on the header of thefirst SOAP message 200. In an exemplary embodiment, the router 205 is anenterprise service-oriented architecture (“eSOA”) with HTTP headerrouting. When the inputs include an aircraft identifier, it isdetermined whether data relating to the aircraft having the aircraftidentifier is stored within the first legacy computer system 20 or thesecond legacy computer system 25. When the inputs include an employeeidentifier, the system 10 determines whether data, such asqualifications and certifications, relating to the employee identifieris stored in the first legacy computer system 20 or the second legacycomputer system 25.

At the step 170, if the data relating to the inputs is associated withthe first legacy computer system 20, then the generic command istransformed into a first operating system command. In an exemplaryembodiment, transforming the generic command to the first operatingsystem command includes generating, at an application 210 (shown in FIG.6D) that is different from the SAFE application 15, a second SOAPmessage 215 (shown in FIG. 6E) using the first SOAP message 200, thesecond SOAP message 215 having a first command stack. Then, at a thirdapplication 220, a second command stack using the second SOAP message215 is generated, with the second command stack being used to executethe generic command at the first legacy computer system 20. Thus, thesecond SOAP message 215 is transformed or used to create a firstoperating system command that is executable by the first legacy computersystem 20, which includes the FOS 20 a.

At the step 175, if the data relating to the inputs is associated withthe second legacy computer system 25, then the generic command istransformed into a second operating system command. In an exemplaryembodiment, transforming the generic command to the second operatingsystem command includes generating, at an application 225 (shown in FIG.6C) that is different from the SAFE application 15 and the applications210 and 220, a third SOAP message 230 using the first SOAP message 200.The third SOAP message 230 is received at an application 235 and istransformed or used to create a second operating system command that isexecutable by the second legacy computer system 25, which includes theSCEPTRE system 85. Generally, a SCEPTRE service sends an XML filerepresenting a SCEPTRE “screen” to GT.

At the step 180, the first operating system command is executed orprocessed by the first legacy computer system 20. In an exemplaryembodiment, the generic command may be to update or edit the datarelating to the inputs, and executing the first operating system commandupdates data relating to the inputs in the first legacy computer system20. When executing the first operating system command, the application220 generates a fourth SOAP message 240 (shown in FIG. 6D), which isreceived and then sent by the application 210. The router 205 receivesthe fourth SOAP message 240 and then generates, based on the fourth SOAPmessage 240, a fifth SOAP message 245 (shown in FIG. 6C). The fifth SOAPmessage 245 is received at the API 195.

At the step 185, the second operating system command is executed orprocessed by the second legacy computer system 25. In response toreceipt of the XML file representing the SCEPTRE “screen”, GT sends“screen” to SCEPTRE and provides an XML response to the SCEPTRE service.The SCEPTRE service then generate and sends a sixth SOAP message 250(shown in FIG. 6C) that is sent to the application 225, which generatesa seventh SOAP message 255 based on the sixth SOAP message 250. At therouter 205, the sixth SOAP message 250 is transformed into the fifthSOAP message 245. The fifth SOAP message 245 is received at the API 195.

At the step 190, the SAFE application 15 displays at least a portion ofthe data related to the inputs on the user interface 30 a using a webbrowser. Based on the fifth SOAP message 245, the API 195 sends a RESTresponse such that a webpage, which contains results viewable by theuser, is displayed on the user interface 30 a. Considering the webpagecontaining results viewable by the user is based on the fifth SOAPmessage 245, which is a result of either the execution of the firstoperating system command or the second operating system command, theview to the user is independent of the first legacy computer system 20and the second legacy computer system 25. The SAFE application 15provides a single common front end application that provides similarviews to the user regardless of whether the user is accessing data inthe first legacy computer system 20 or the second legacy computer system25. In an exemplary embodiment, the SAFE application 15 and/or thesystem 10 is a tool to direct mechanics to backend systems relating toan aircraft maintenance logbook, training and/or qualifications, OilService programs, and FLIFO by allowing them to enter maintenanceinformation into legacy systems without having extensive training onthose systems. In an exemplary embodiment and in regards to aircraftmaintenance logbook, data is entered into each of the legacy systemsusing unique forms for each legacy system, with the unique forms havinga common (to that legacy system) look and order of fields. In anexemplary embodiment, the labels and data field nomenclature of the SAFEwebpage incorporate both the processes of the first legacy airline andthe second legacy airline, with differences between those processesbeing denoted by greying out comments within the form presented by theSAFE webpage. In an exemplary embodiment, maintenance release,placarding, and logbook processes have a common look and feel whenpresented by the SAFE application 15. The operational manuals/proceduresof the first and second legacy airlines are harmonized using the SAFEapplication 15. In an exemplary embodiment and in regards to trainingand/or qualifications, management and mechanics may access anindividual's current training and/or qualifications from both the firstlegacy computer system 20 and the second legacy computer system 25, toensure that mechanics are not assigned to work on aircraft and/or tasksthat they are not currently qualified on, per each of the first andsecond legacy airlines' training requirements. In an exemplaryembodiment, the SAFE application 15 creates an automation to alertmechanics of their qualifications, upon selection of nose number of anaircraft, if he or she is qualified to perform the task. In an exemplaryembodiment and in regards to the FLIFO, the SAFE application 15 maypresent to the mechanic, via a webpage displayed on the graphical userinterface 30 a, current aircraft location and routing data. In anexemplary embodiment, displaying at least as portion of the data relatedto the inputs on the user interface 30 a may include routing the user toa webpage in a web browser that displays links for the user, such as amechanic, for the various mechanic activities based on the carrier.Additionally, the SAFE application 15 is configured to restrict viewsand entries to the SAFE application 15 based on the user roles as wellas qualifications, determined by the employee identifier, in order tohelp ensure regulatory compliance. For example, when the user is anunauthorized user, no work instructions regarding the task is displayedto the user thereby preventing the user from completing the work.

FIGS. 7A-7C are configuration views of the system 10, according to anexemplary embodiment. In an exemplary embodiment, the SAFE application15 is a standard multitier application with a base of services exposedvia the eSOA. Generally, the SAFE application 15 is internet accessiblein order to provide access to computing devices, such as the computer 30via the network 35, such as a cellular network. In an exemplaryembodiment, the system 10 includes a web application server, which inseveral exemplary embodiments includes and/or executes one or moreweb-based programs, Intranet-based programs, and/or any combinationthereof. In an exemplary embodiment, the network 35 includes theInternet, one or more local area networks, one or more wide areanetworks, one or more cellular networks, one or more wireless networks,one or more voice networks, one or more data networks, one or morecommunication systems, and/or any combination thereof. In an exemplaryembodiment, the system 10 includes one or more computer processors and anon-transitory computer readable medium operably coupled thereto.Instructions accessible to, and executable by, the computer processorare stored on the non-transitory computer readable medium. A database isalso stored in the non-transitory computer readable medium. In anexemplary embodiment, the web application server is adapted to be incommunication with the computer 30, the first legacy computer system 20,and the second legacy computer system 25. In an exemplary embodiment,the non-transitory computer readable medium is at least part of one, orboth, of the computer 30 and the application server. In an exemplaryembodiment, the one or more computer processors is at least part of one,or both, of the computer 30 and the application server.

In one or more exemplary embodiments, the computer 30 includes acomputer processor and a computer readable medium operably coupledthereto. Instructions accessible to, and executable by, the computerprocessor are stored on the computer readable medium. A database is alsostored in the computer readable medium. In an exemplary embodiment, thecomputer 30 includes an input device and an output device. In anexemplary embodiment, web browser software is stored in the computerreadable medium of the computer 30. In an exemplary embodiment, theinput device is a keyboard, mouse, or other device coupled the computer30 that sends instructions to the computer 30. In an exemplaryembodiment, the input device and the output device include the usergraphical interface 30 a, which, in several exemplary embodiments, is inthe form of, or includes, one or more digital displays, one or moreliquid crystal displays, one or more cathode ray tube monitors, and/orany combination thereof. In an exemplary embodiment, the input device isthe output device, and the output device is the input device. In severalexemplary embodiments, the computer 30 is a mobile device or is a thinclient. In several exemplary embodiments, the computer 30 is a thickclient. In several exemplary embodiments, the computer 30 functions asboth a thin client and a thick client. In several exemplary embodiments,the computer 30 is, or includes, a telephone, a personal computer, apersonal digital assistant, a cellular telephone, other types oftelecommunications devices, other types of computing devices, and/or anycombination thereof. In several exemplary embodiments, the computer 30includes a plurality of remote user devices. In an exemplary embodiment,the computer 30 is capable of running or executing an application.

FIGS. 8A-8C illustrate another process of the system 10, the processbeing generally referred to by the reference numeral 260. In response tothe user logging into the system 10 via the webpage of the SAFEapplication 15, the SAFE application 15 determines whether the user is“authorized” based on the user's role. If the user is not authorized,then the process ends. If the user is authorized, then the SAFEapplication 15 determines if the legacy employer of the user is thefirst legacy airline or the second legacy airline. If the user has alegacy employer that is the first legacy airline and data associatedwith the user is associated with the first legacy computer system 20,then the SAFE application 15 retrieves the qualifications of the userfrom the SABA system 115. However, the retrieval of qualifications ofthe user from the SABA system 115 may be omitted. If the user has alegacy employer that is the second legacy airline and data associatedwith the user is associated with the second legacy computer system 25,then the SAFE application 15 retrieves the qualifications of the userfrom the Learning Path system 110. After retrieving the qualification ofthe user, the user inputs the nose number of an aircraft. In response,the SAFE application 15 retrieves any available augmented dataassociated with the aircraft in the Attributes system 90 and combinesany augmented data with data retrieved from the Equipment Servicessystem 70 that is associated with the aircraft. Then, the SAFEapplication 15 determines if there is a nose number collision. If so,then the SAFE Application 15 requests and receives, using a webpage,from the user the fleet type of the aircraft. Next, the SAFE application15 retrieves FLIFO and displays data and links to the user using anotherwebpage.

In several exemplary embodiments, the SAFE application 15 providesmechanics the functionality to view and enter aircraft maintenancediscrepancies, including minimum equipment lists (“MELs”), via thesingle common front end application. In an exemplary embodiment, allaspects of the log page entry are included in the SAFE application 15(i.e., part changes, lower order checks, MELs, Maintenance Item Sheet(“MIC sheet”), etc.). In an exemplary embodiment, all applicable dataitems displayed by the SAFE application 15 are harmonized and match thecurrent log book format. In an exemplary embodiment, the SAFEapplication 15 updates back end systems automatically without themechanic having to know data entry formats for either the first legacycomputer system 20 or the second legacy computer system 25. In anexemplary embodiment, the SAFE application 15 directs the mechanic inthe “right” direction from an aircraft “maintenance program”perspective.

In several exemplary embodiments, a first commercial airline carrierthat is no longer in operation is associated with the first legacyairline, a second commercial airline carrier that is no longer inoperation is associated with the second legacy airline, and a thirdcommercial airline carrier that is in operation and was formed by amerger of the first and second commercial airlines implements the SAFEapplication 15 to easily view, edit, and delete data within the firstlegacy computer system 20 and the second legacy computer system 25.

In several exemplary embodiments, the SAFE application 15 ensures thatmechanics are qualified to perform all assigned maintenance tasks. Inseveral exemplary embodiments, the SAFE application 15 allows forharmonization of the Oil Servicing Program and avoids confusion andadditional training for mechanics before the aircrafts from the firstlegacy airline and the second legacy airline are consolidated into onemaintenance program. In several exemplary embodiments, the SAFEapplication 15 gives more assistance and information to the mechanicsfor duplicate aircraft by providing (displaying on a user interface 30a) current flight and routing information. In an exemplary embodiment,this supports functionality that locks the aircraft final weight balanceinformation if critical maintenance functions are not performed, such asthe checks or transit checks for Extended-range twin-engine operations(“ETOP”). In several exemplary embodiments, the SAFE application 15protects mechanics and the third commercial airline from non-compliance.In an exemplary embodiment, the SAFE application 15 simplifies trainingrequirements of a large workforce and provides automation to help themechanics get to the proper legacy systems. In several exemplaryembodiments, the SAFE application 15 reconciles differences in dataschema between the first legacy computer system 20 and the second legacycomputer system 25 in order to have a united interface for the thirdcommercial airline. In several exemplary embodiments, the SAFEapplication 15 includes a single interface that allows mechanics toview, add, or edit data from two different legacy systems (i.e., thefirst legacy computer system 20 and the second legacy computer system25). In several exemplary embodiments, the SAFE application 15 is aweb-based data entry portal that is a tool to channel mechanics to acompliant process. In an exemplary embodiment, the SAFE application 15allows for common data sources to be directed to different legacysystems (i.e., the first legacy computer system 20 and the second legacycomputer system 25) as needed and maintains a well-structured data mapfor future system migration. In an exemplary embodiment, the SAFEapplication 15 is a common front end for AMT's that allows each AMT toenter pertinent aircraft maintenance information into legacy systems(i.e., the first legacy computer system 20 and the second legacycomputer system 25) without having extensive training on those systems.In an exemplary embodiment, the SAFE application 15 has a database thatallows it to track aircraft in both fleets (AA and US) before and afterthe aircraft is migrated to the “end state” system.

In several exemplary embodiments, the system 10 includes an arrangementof elements (i.e., the SAFE application 15, the first legacy computersystem 20, and the second legacy computer system 25) that is a technicalimprovement over the previous ways of accessing data in two legacycomputer systems. The system 10 is a technical solution to theaforementioned problems associated with the merging of two legacyairlines and their computer systems and maintenance crews. Moreover, theSAFE application 15 enforces a layer of input validation and controls toresult in faster and more efficient data entry into the first legacycomputer system 20 and the second legacy computer system 25. In anexemplary embodiment, the SAFE application 15 joins two disparatesystems (i.e., the first legacy computer system 20 and the second legacycomputer system 25) into a unified interface. In order to join twodisparate systems, the SAFE application 15 reconciles the differences inthe data schema of the first legacy computer system 20 and the secondlegacy computer system 25.

In several exemplary embodiments, the SAFE application 15 providesautomation that forces the mechanics into the correct legacy carriersystem. In an exemplary embodiment, the first legacy computer system 20has a portal for mechanics, which is ViaNet, and the second legacycomputer system 25 has a portal for mechanics, which is Mechanic homepage. In an exemplary embodiment, M&E requires similar style links,accessible from all work stations (elimination of LUS Single Sign-onProcess (“SSO”)) that have the logic built into them to direct them tothe correct legacy system, based on the mechanic entering the nosenumber at some point in the decision logic. In an exemplary embodiment,the SAFE application 15 is a common website to be used by all of theAMT's and is intended to embrace the culture of both the first and thesecond legacy airlines and help communicate integration changes.

In several exemplary embodiments, the system 10 and/or the method 150unify the maintenance business process across both legacy airlines (AAand US Airways) by which aircraft mechanics access aircraft attributes(e.g., engine type, registration number, etc.) and maintenance historyinformation, and create new logbook entries via a single user interface(i.e., the SAFE application 15) that is independent of the legacysystems to which it communicates. In an exemplary embodiment, the SAFEapplication 15 allows all mechanics, whether from legacy AA or legacy USAirways, to follow a single process to accomplish and record their work,even where there may be vast differences in how that data is stored andmanaged on the legacy systems. In an exemplary embodiment, this resultsin improved efficiency in training and business processes, but it alsosignificantly reduces risk of incorrect data entry or other mistakes,considering mechanics are not required to alternate between two entirelydifferent processes dependent upon which aircraft they may be workingon. Thus, mechanics can access information such as aircraft model,engine type, seating configuration, etc., routing data, proceduremanuals and logbook history using the SAFE application 15. In anexemplary embodiment, mechanics can also create new logbook entriesusing the SAFE application 15, including all types of deferrals, detailsof parts and labor required, and other information essential to planningand scheduling maintenance work on an aircraft without being familiarwith any of the archaic commands typically used in legacy applications.

In several exemplary embodiments, the SAFE application 15 and/or themethod 150 eliminates the need to learn, understand, and use archaicDOS-based commands and codes associated with each of the legacy systems;reduces the risk that a mechanic might inadvertently follow an incorrectprocedure considering the SAFE application 15 unifies processes acrossthe third commercial airline; helps facilitate quicker integration ofthe two legacy airlines by removing any differences in businessprocesses, while also enforcing compliance with safety requirements; isavailable via most standard web browsers, rather than being limited toproprietary system and hardware; allows for greater range of inputvalidation and error handling; and enables greater use of pre-populateddata to reduce invalid entries and typographical errors.

In several exemplary embodiments, the SAFE application 15 and/or themethod 150 prevents training aircraft mechanics from one legacy carrieron a system specific to the other legacy carrier. In several exemplaryembodiments, the SAFE application 15 and/or the method 150 enables thebusiness unit to immediately achieve workforce unity, as opposed tocross-training all mechanics on both legacy carrier systems. In severalexemplary embodiments, the SAFE application 15 and/or the method 150eliminates the need for cross-training aircraft mechanics, thus reducingthe risk associated with introducing new procedures that are notapplicable in all situations. In several exemplary embodiments, the SAFEapplication 15 and/or the method 150 supersedes manual processes, suchas hand-written log entries, and thus reduces opportunities for error inthe misreading written entries.

In several exemplary embodiments, the system 10 and the method 150according to respective exemplary embodiments implement an applicationfor one or more airlines capable of supporting all event loggingrequirements, and connect to non-TPF-based flight operationsapplications via a message handling system, and are compatible withexisting and planned hardware and flexible to allow for expansion ifrequired. In several exemplary embodiments, such a message handlingsystem may be referred to as “Flight Hub.” In several exemplaryembodiments, one or more exemplary embodiments of such a messagehandling system, or Flight Hub, may be described and illustrated inwhole or in part in U.S. application Ser. No. 11/119,787, filed May 2,2005, which issued on Dec. 11, 2012 as U.S. Pat. No. 8,332,473 to Foutset al., the entire disclosures of which are hereby incorporated hereinby reference.

In several exemplary embodiments, the system 10 and the method 150according to respective exemplary embodiments implement an applicationfor one or more airlines that manages maintenance activities. In severalexemplary embodiments, such a maintenance management application may bereferred to as “ViaNet.” In several exemplary embodiments, one or moreexemplary embodiments of such a maintenance management application, orViaNet, may be described and illustrated in whole or in part in U.S.application Ser. No. 12/475,092, filed May 29, 2009, which issued onAug. 28, 2012 as U.S. Pat. No. 8,255,097 to Wander, the entiredisclosures of which are hereby incorporated herein by reference.

In an exemplary embodiment, as illustrated in FIG. 9 with continuingreference to FIGS. 1-5, 6A-6E, 7A-7C, and 8A-8C, an illustrative node900 for implementing one or more of the exemplary embodiments describedabove, illustrated in FIGS. 1-5, 6A-6E, 7A-7C, and 8A-8C is depicted.The node 900 includes a microprocessor 900 a, an input device 900 b, astorage device 900 c, a video controller 900 d, a system memory 900 e, adisplay 900 f, and a communication device 900 g all interconnected byone or more buses 900 h. In several exemplary embodiments, the storagedevice 900 c may include a floppy drive, hard drive, CD-ROM, opticaldrive, any other form of storage device and/or any combination thereof.In several exemplary embodiments, the storage device 900 c may include,and/or be capable of receiving, a floppy disk, CD-ROM, DVD-ROM, or anyother form of computer-readable medium that may contain executableinstructions. In several exemplary embodiments, the communication device900 g may include a modem, network card, or any other device to enablethe node to communicate with other nodes. In several exemplaryembodiments, any node represents a plurality of interconnected (whetherby intranet or Internet) computer systems, including without limitation,personal computers, mainframes, personal digital assistants (“PDAs”),smartphones and cell phones.

In several exemplary embodiments, one or more of the components of thesystems described above, illustrated in FIGS. 1-5, 6A-6E, 7A-7C, and8A-8C include at least the node 900 and/or components thereof, and/orone or more nodes that are substantially similar to the node 900 and/orcomponents thereof. In several exemplary embodiments, one or more of theabove-described components of the node 900 and/or the system illustratedin FIGS. 1-5, 6A-6E, 7A-7C, and 8A-8C, include respective pluralities ofsame components.

In several exemplary embodiments, the system 10 illustrated in FIGS.1-5, 6A-6E, 7A-7C, and 8A-8C includes a computer program that includes aplurality of instructions, data, and/or any combination thereof; anapplication written in, for example, Arena, HyperText Markup Language(HTML), Cascading Style Sheets (CSS), JavaScript, Extensible MarkupLanguage (XML), asynchronous JavaScript and XML (Ajax), and/or anycombination thereof; a web-based application written in, for example,Java or Adobe Flex, which in several exemplary embodiments pullsreal-time information from one or more servers, automatically refreshingwith latest information at a predetermined time increment; or anycombination thereof.

In several exemplary embodiments, a computer or a computer systemtypically includes at least hardware capable of executing machinereadable instructions, as well as the software for executing acts(typically machine-readable instructions) that produce a desired result.In several exemplary embodiments, a computer system may include hybridsof hardware and software, as well as computer sub-systems.

In several exemplary embodiments, hardware generally includes at leastprocessor-capable platforms, such as client-machines (also known aspersonal computers or servers), and hand-held processing devices (suchas smart phones, tablet computers, PDAs, or personal computing devices(PCDs), for example). In several exemplary embodiments, hardware mayinclude any physical device that is capable of storing machine-readableinstructions, such as memory or other data storage devices. In severalexemplary embodiments, other forms of hardware include hardwaresub-systems, including transfer devices such as modems, modem cards,ports, and port cards, for example.

In several exemplary embodiments, software includes any machine codestored in any memory medium, such as RAM or ROM, and machine code storedon other devices (such as floppy disks, flash memory, or a CD ROM, forexample). In several exemplary embodiments, software may include sourceor object code. In several exemplary embodiments, software encompassesany set of instructions capable of being executed on a node such as, forexample, on a client machine or server.

In several exemplary embodiments, combinations of software and hardwarecould also be used for providing enhanced functionality and performancefor certain embodiments of the present disclosure. In an exemplaryembodiment, software functions may be directly manufactured into asilicon chip. Accordingly, it should be understood that combinations ofhardware and software are also included within the definition of acomputer system and are thus envisioned by the present disclosure aspossible equivalent structures and equivalent methods.

In several exemplary embodiments, computer readable mediums include, forexample, passive data storage, such as a random access memory (RAM) aswell as semi-permanent data storage such as a compact disk read onlymemory (CD-ROM). One or more exemplary embodiments of the presentdisclosure may be embodied in the RAM of a computer to transform astandard computer into a new specific computing machine. In severalexemplary embodiments, data structures are defined organizations of datathat may enable an embodiment of the present disclosure. In an exemplaryembodiment, a data structure may provide an organization of data, or anorganization of executable code.

In several exemplary embodiments, a database may be any standard orproprietary database software, such as Oracle, Microsoft Access, SyBase,or DBase II, for example. In several exemplary embodiments, the databasemay have fields, records, data, and other database elements that may beassociated through database specific software. In several exemplaryembodiments, data may be mapped. In several exemplary embodiments,mapping is the process of associating one data entry with another dataentry. In an exemplary embodiment, the data contained in the location ofa character file can be mapped to a field in a second table. In severalexemplary embodiments, the physical location of the database is notlimiting, and the database may be distributed. In an exemplaryembodiment, the database may exist remotely from the server, and run ona separate platform. In an exemplary embodiment, the database may beaccessible across the Internet. In several exemplary embodiments, morethan one database may be implemented.

In several exemplary embodiments, a plurality of instructions stored ona computer readable medium may be executed by one or more processors tocause the one or more processors to carry out or implement in whole orin part the above-described operation of each of the above-describedexemplary embodiments of the system, the method, and/or any combinationthereof. In several exemplary embodiments, such a processor may includeone or more of the microprocessor 900 a, any processor(s) that are partof the components of the system, and/or any combination thereof, andsuch a computer readable medium may be distributed among one or morecomponents of the system. In several exemplary embodiments, such aprocessor may execute the plurality of instructions in connection with avirtual computer system. In several exemplary embodiments, such aplurality of instructions may communicate directly with the one or moreprocessors, and/or may interact with one or more operating systems,middleware, firmware, other applications, and/or any combinationthereof, to cause the one or more processors to execute theinstructions.

A method of accessing data in one of a first legacy computer system thathas a first operating system and a second legacy computer system thathas a second operating system that is different from the first operatingsystem has been described that includes providing a front endapplication that is in communication with each of the first legacycomputer system and the second legacy computer system, wherein the frontend application is displayed on a graphical user interface of acomputer; receiving, via a first webpage displayed on the computer andusing the front end application, a plurality of inputs that includes: ageneric command that is generic to the first operating system and thesecond operating system; and an aircraft identifier; determining, basedon the aircraft identifier, whether data related to the aircraftidentifier is associated with the first legacy computer system or thesecond legacy computer system; if the data related to the aircraftidentifier is associated with the first legacy computer system, thentransforming the generic command to a first operating system command;and if the data related to the aircraft identifier is associated withthe second legacy computer system, then transforming the generic commandto a second operating system command; wherein the first operating systemcommand is different from the second operating system command, and thusthe transformation of the generic command to either the first operatingsystem command or the second operating system command reconcilesdifferences in data schema associated with the first and the secondlegacy computer systems and allows for the front end application to be asingle common front end application to access data within both the firstand second legacy computer systems. In an exemplary embodiment, at leastone of the first legacy computer system and the second legacy computersystem is a non-web based system; and the single common front endapplication is a web-based application configured to access the firstlegacy computer system and the second legacy computer system therebyallowing a user of the single common front end application to access thefirst legacy computer system and the second legacy computer system usinga web browser. In an exemplary embodiment, when the data related to theaircraft identifier is associated with the first legacy computer system,the method further includes executing the first operating systemcommand; and wherein at least a portion of the data related to theaircraft identifier is displayed in a second webpage on the computerusing the single common front end application in response to theexecution of the first operating system command. In an exemplaryembodiment, the generic command is to search for the data related to theaircraft identifier and the first operating system command is to searchfor the data related to the aircraft identifier; and the at least aportion of the data related to the aircraft identifier includesmaintenance history for the aircraft associated with the aircraftidentifier. In an exemplary embodiment, the plurality of inputs furtherincludes a user identifier that is associated with a user of the singlecommon front end application; the method further includes customizing athird webpage using the single common front end application based on theuser identifier received; and customizing the third webpage based on theuser identifier received prevents displaying work instructions to theuser when the user is an unauthorized user. In an exemplary embodiment,the single common front end application validates at least one inputfrom the plurality of inputs. In an exemplary embodiment, transformingthe generic command to the first operating system command includes:generating a JSON object that includes at least one input from theplurality of inputs; generating, using the JSON object, a first SOAPmessage including a header that includes a first legacy computer systemidentifier; identifying, at a second application, the first legacycomputer system identifier in the first SOAP message; generating, usingthe first SOAP message, a second SOAP message at a third application,the second SOAP message including a first command stack; and generating,at a fourth application, a second command stack using the second SOAPmessage, wherein the second command stack is used to generate the firstoperating system command. In an exemplary embodiment, transforming thegeneric command to the second operating system command includes:generating a JSON object that includes at least one input from theplurality of inputs; generating, using the JSON object, a third SOAPmessage including a header that includes a second legacy computer systemidentifier; identifying, at a fifth application, the second legacycomputer system identifier in the third SOAP message; and generating, ata sixth application, a fourth SOAP message using the third SOAP message,wherein the fourth SOAP message is used to generate the second operatingsystem command. In an exemplary embodiment, the first operating systemis a SABRE system. In an exemplary embodiment, the second operatingsystem is a SCEPTRE system.

A system has been described that includes a first legacy computer systemthat has a first operating system; a second legacy computer system thathas a second operating system that is different from the first operatingsystem; a computer; and a non-transitory computer readable medium, thenon-transitory computer readable medium including a plurality ofinstructions that are executable by one or more processors, theplurality of instructions including: instructions that cause the one ormore processors to receive a plurality of inputs from the computer, theplurality of instructions including: a generic command that is genericto the first operating system and the second operating system; and anaircraft identifier; instructions that cause the one or more processorsto determine, based on the aircraft identifier, whether data related tothe aircraft identifier is associated with the first legacy computersystem or the second legacy computer system; instructions that cause theone or more processors to transform the generic command to a firstoperating system command if the data related to the aircraft identifieris associated with the first legacy computer system; and instructionsthat cause the one or more processors to transform the generic commandto a second operating system command if the data related to the aircraftidentifier is associated with the second legacy computer system; whereinthe first operating system command is different from the secondoperating system command, and thus the transformation of the genericcommand to either the first operating system command or the secondoperating system command reconciles differences in data schemaassociated with the first and the second legacy computer systems andallows for a single common front end application to be displayed on thecomputer and to access data within both the first and second legacycomputer systems. In an exemplary embodiment, the system also includesan application server adapted to be in communication with each of thecomputer, the first legacy computer system, and the second legacycomputer system, wherein the non-transitory computer readable medium isat least part of one, or both, of the computer and the applicationserver, and wherein the one or more processors is at least part of one,or both, of the computer and the application server. In an exemplaryembodiment, at least one of the first legacy computer system and thesecond legacy computer system is a non-web based system; and wherein thesingle common front end application is a web-based applicationconfigured to access the first legacy computer system and the secondlegacy computer system thereby allowing a user of the single commonfront end application to access the first legacy computer system and thesecond legacy computer system using a web browser. In an exemplaryembodiment, when the data related to the aircraft identifier isassociated with the first legacy computer system; wherein the pluralityof instructions further include instructions that cause the one or moreprocessors to execute the first operating system command; and wherein atleast a portion of the data related to the aircraft identifier isdisplayed in a webpage on the computer using the common front endapplication in response to the execution of the first operating systemcommand. In an exemplary embodiment, the generic command is to searchfor the data related to the aircraft identifier and the first operatingsystem command is to search for the data related to the aircraftidentifier; and wherein at least a portion of the data related to theaircraft identifier includes maintenance history for the aircraftassociated with the aircraft identifier. In an exemplary embodiment, theplurality of inputs further includes a user identifier that isassociated with a user of the common front end application; theplurality of instructions further include instructions that cause theone or more processors to customize a third webpage to be displayedusing the single common front end application based on the useridentifier received; and customizing the third webpage based on the useridentifier received prevents displaying work instructions to the userwhen the user is an unauthorized user. In an exemplary embodiment, thesingle common front end application validates at least one inputs fromthe plurality of inputs. In an exemplary embodiment, the instructionsthat cause the one or more processors to transform the generic commandto the first operating system command if the data related to theaircraft identifier is associated with the first legacy computer systemincludes: instructions that cause the one or more processors to generatea JSON object that includes at least one input from the plurality ofinputs; instructions that cause the one or more processors to generate,using the JSON object, a first SOAP message including a header thatincludes a first legacy computer system identifier; instructions thatcause the one or more processors to identify, at a second application,the first legacy computer system identifier in the first SOAP message;instructions that cause the one or more processors to generate, usingthe first SOAP message, a second SOAP message at a third application,the second SOAP message including a first command stack; andinstructions that cause the one or more processors to generate, at afourth application, a second command stack using the second SOAPmessage, wherein the second command stack is used to generate the firstoperating system command. In an exemplary embodiment, the instructionsthat cause the one or more processors to transform the generic commandto the second operating system command if the data related to theaircraft identifier is associated with the second legacy computer systemincludes: instructions that cause the one or more processors to generatea JSON object that includes at least one input from the plurality ofinputs; instructions that cause the one or more processors to generate,using the JSON object, a third SOAP message including a header thatincludes a second legacy computer system identifier; instructions thatcause the one or more processors to identify, at a fifth application,the second legacy computer system identifier in the third SOAP message;and instructions that cause the one or more processors to generate, at asixth application, a fourth SOAP message using the third SOAP message,wherein the fourth SOAP message is used to generate the second operatingsystem command. In an exemplary embodiment, the first operating systemis a SABRE system and the second operating system is a SCEPTRE system.

It is understood that variations may be made in the foregoing withoutdeparting from the scope of the present disclosure. For example, insteadof, or in addition to transportation transactions often conducted in thecourse of airline industry business, aspects of the present disclosureare applicable and/or readily adaptable to transportation transactionsconducted in other industries, including rail, bus, cruise and othertravel or shipping industries, rental car industries, hotels and otherhospitality industries, entertainment industries, and other industries.In an exemplary embodiment, aspects of the present disclosure arereadily applicable and/or readily adaptable to legacy systems within avariety of industries, such as shipping industries, train-relatedindustries, etc.

In several exemplary embodiments, the elements and teachings of thevarious illustrative exemplary embodiments may be combined in whole orin part in some or all of the illustrative exemplary embodiments. Inaddition, one or more of the elements and teachings of the variousillustrative exemplary embodiments may be omitted, at least in part,and/or combined, at least in part, with one or more of the otherelements and teachings of the various illustrative embodiments.

Any spatial references such as, for example, “upper,” “lower,” “above,”“below,” “between,” “bottom,” “vertical,” “horizontal,” “angular,”“upwards,” “downwards,” “side-to-side,”“left-to-right,” “right-to-left,”“top-to-bottom,” “bottom-to-top,” “top,” “bottom,” “bottom-up,”“top-down,” etc., are for the purpose of illustration only and do notlimit the specific orientation or location of the structure describedabove.

In several exemplary embodiments, while different steps, processes, andprocedures are described as appearing as distinct acts, one or more ofthe steps, one or more of the processes, and/or one or more of theprocedures may also be performed in different orders, simultaneouslyand/or sequentially. In several exemplary embodiments, the steps,processes and/or procedures may be merged into one or more steps,processes and/or procedures.

In several exemplary embodiments, one or more of the operational stepsin each embodiment may be omitted. Moreover, in some instances, somefeatures of the present disclosure may be employed without acorresponding use of the other features. Moreover, one or more of theabove-described embodiments and/or variations may be combined in wholeor in part with any one or more of the other above-described embodimentsand/or variations.

Although several exemplary embodiments have been described in detailabove, the embodiments described are exemplary only and are notlimiting, and those skilled in the art will readily appreciate that manyother modifications, changes and/or substitutions are possible in theexemplary embodiments without materially departing from the novelteachings and advantages of the present disclosure. Accordingly, allsuch modifications, changes and/or substitutions are intended to beincluded within the scope of this disclosure as defined in the followingclaims. In the claims, any means-plus-function clauses are intended tocover the structures described herein as performing the recited functionand not only structural equivalents, but also equivalent structures.Moreover, it is the express intention of the applicant not to invoke 35U.S.C. § 112, paragraph 6 for any limitations of any of the claimsherein, except for those in which the claim expressly uses the word“means” together with an associated function.

What is claimed is:
 1. A system comprising: a first legacy computersystem that has a first operating system; a second legacy computersystem that has a second operating system that is different from thefirst operating system; a computer; and a non-transitory computerreadable medium, the non-transitory computer readable medium comprisinga plurality of instructions that are executable by one or moreprocessors, the plurality of instructions comprising: instructions thatcause the one or more processors to receive a plurality of inputs fromthe computer, the plurality of inputs comprising: a generic command thatis generic to the first operating system and the second operatingsystem; and an aircraft identifier; instructions that cause the one ormore processors to determine, based on the aircraft identifier, whetherdata related to the aircraft identifier is associated with the firstlegacy computer system or the second legacy computer system;instructions that cause the one or more processors to transform thegeneric command to a first operating system command if the data relatedto the aircraft identifier is associated with the first legacy computersystem; and instructions that cause the one or more processors totransform the generic command to a second operating system command ifthe data related to the aircraft identifier is associated with thesecond legacy computer system; wherein the first operating systemcommand is different from the second operating system command, and thusthe transformation of the generic command to either the first operatingsystem command or the second operating system command reconcilesdifferences in data schema associated with the first and the secondlegacy computer systems and allows for a single common front endapplication to be displayed on the computer and to access data withinboth the first and second legacy computer systems.
 2. The system ofclaim 1, further comprising an application server adapted to be incommunication with each of the computer, the first legacy computersystem, and the second legacy computer system, wherein thenon-transitory computer readable medium is at least part of one, orboth, of the computer and the application server, and wherein the one ormore processors is at least part of one, or both, of the computer andthe application server.
 3. The system of claim 1, wherein at least oneof the first legacy computer system and the second legacy computersystem is a non-web based system; and wherein the single common frontend application is a web-based application configured to access thefirst legacy computer system and the second legacy computer systemthereby allowing a user of the single common front end application toaccess the first legacy computer system and the second legacy computersystem using a web browser.
 4. The system of claim 1, wherein, when thedata related to the aircraft identifier is associated with the firstlegacy computer system; wherein the plurality of instructions furthercomprise instructions that cause the one or more processors to executethe first operating system command; and wherein at least a portion ofthe data related to the aircraft identifier is displayed in a webpage onthe computer using the single common front end application in responseto the execution of the first operating system command.
 5. The system ofclaim 1, wherein the generic command is to search for the data relatedto the aircraft identifier and the first operating system command is tosearch for the data related to the aircraft identifier; and wherein atleast a portion of the data related to the aircraft identifier includesmaintenance history for the aircraft associated with the aircraftidentifier.
 6. The system of claim 1, wherein the plurality of inputsfurther comprises a user identifier that is associated with a user ofthe single common front end application; wherein the plurality ofinstructions further comprise instructions that cause the one or moreprocessors to customize a third webpage to be displayed using the singlecommon front end application based on the user identifier received; andwherein customizing the third webpage based on the user identifierreceived prevents displaying work instructions to the user when the useris an unauthorized user.
 7. The system of claim 1, wherein the singlecommon front end application validates at least one input from theplurality of inputs.
 8. The system of claim 1, wherein the instructionsthat cause the one or more processors to transform the generic commandto the first operating system command if the data related to theaircraft identifier is associated with the first legacy computer systemcomprises: instructions that cause the one or more processors togenerate a JSON object that includes at least one input from theplurality of inputs; instructions that cause the one or more processorsto generate, using the JSON object, a first SOAP message comprising aheader that includes a first legacy computer system identifier;instructions that cause the one or more processors to identify, at asecond application, the first legacy computer system identifier in thefirst SOAP message; instructions that cause the one or more processorsto generate, using the first SOAP message, a second SOAP message at athird application, the second SOAP message comprising a first commandstack; and instructions that cause the one or more processors togenerate, at a fourth application, a second command stack using thesecond SOAP message, wherein the second command stack is used togenerate the first operating system command.
 9. The system of claim 1,wherein the instructions that cause the one or more processors totransform the generic command to the second operating system command ifthe data related to the aircraft identifier is associated with thesecond legacy computer system comprises: instructions that cause the oneor more processors to generate a JSON object that includes at least oneinput from the plurality of inputs; instructions that cause the one ormore processors to generate, using the JSON object, a third SOAP messagecomprising a header that includes a second legacy computer systemidentifier; instructions that cause the one or more processors toidentify, at a fifth application, the second legacy computer systemidentifier in the third SOAP message; and instructions that cause theone or more processors to generate, at a sixth application, a fourthSOAP message using the third SOAP message, wherein the fourth SOAPmessage is used to generate the second operating system command.
 10. Thesystem of claim 1, wherein the first operating system is a SABRE systemand the second operating system is a SCEPTRE system.
 11. A systemcomprising: a first legacy computer system that has a first operatingsystem; a second legacy computer system that has a second operatingsystem that is different from the first operating system; one or morecomputers configured to: receive a plurality of inputs, the plurality ofinputs comprising a generic command that is generic to the firstoperating system and the second operating system, and an aircraftidentifier; determine, based on the aircraft identifier, whether datarelated to the aircraft identifier is associated with the first legacycomputer system or the second legacy computer system; transform thegeneric command to a first operating system command if the data relatedto the aircraft identifier is associated with the first legacy computersystem; and transform the generic command to a second operating systemcommand if the data related to the aircraft identifier is associatedwith the second legacy computer system; wherein the first operatingsystem command is different from the second operating system command,and thus the transformation of the generic command to either the firstoperating system command or the second operating system commandreconciles differences in data schema associated with the first and thesecond legacy computer systems and allows data to be accessed datawithin both the first and second legacy computer systems; wherein thesystem further comprises a single common front end applicationconfigured to be displayed on at least one of the one or more computersand access the data within the first and second legacy computer systems;wherein the reconciliation of the differences in data schema associatedwith the first and the second legacy computer systems allows for thesingle common front end application to be displayed on the at least oneof the one or more computers, and access the data within the first andsecond legacy computer systems; wherein at least one of the first legacycomputer system and the second legacy computer system is a non-web basedsystem; and wherein the single common front end application is aweb-based application configured to access the first legacy computersystem and the second legacy computer system thereby allowing a user ofthe single common front end application to access the first legacycomputer system and the second legacy computer system using a webbrowser.
 12. The system of claim 11, wherein the single common front endapplication validates at least one input from the plurality of inputs.13. The system of claim 11, wherein the first operating system is aSABRE system and the second operating system is a SCEPTRE system.
 14. Asystem comprising: a first legacy computer system that has a firstoperating system; a second legacy computer system that has a secondoperating system that is different from the first operating system; oneor more computers configured to: receive a plurality of inputs, theplurality of inputs comprising a generic command that is generic to thefirst operating system and the second operating system, and anidentifier; determine, based on the identifier, whether data related tothe identifier is associated with the first legacy computer system orthe second legacy computer system; transform the generic command to afirst operating system command if the data related to the identifier isassociated with the first legacy computer system; and transform thegeneric command to a second operating system command if the data relatedto the identifier is associated with the second legacy computer system;wherein the first operating system command is different from the secondoperating system command, and thus the transformation of the genericcommand to either the first operating system command or the secondoperating system command reconciles differences in data schemaassociated with the first and the second legacy computer systems andallows data to be accessed data within both the first and second legacycomputer systems.
 15. The system of claim 14, further comprising: asingle common front end application configured to be displayed on atleast one of the one or more computers and access the data within thefirst and second legacy computer systems.
 16. The system of claim 15,wherein the reconciliation of the differences in data schema associatedwith the first and the second legacy computer systems allows for thesingle common front end application to be displayed on the at least oneof the one or more computers, and access the data within the first andsecond legacy computer systems.
 17. The system of claim 15, wherein atleast one of the first legacy computer system and the second legacycomputer system is a non-web based system.
 18. The system of claim 17,wherein the single common front end application is a web-basedapplication configured to access the first legacy computer system andthe second legacy computer system thereby allowing a user of the singlecommon front end application to access the first legacy computer systemand the second legacy computer system using a web browser.
 19. Thesystem of claim 15, wherein the identifier is an aircraft identifier.20. The system of claim 15, wherein the first operating system is aSABRE system, and the second operating system is a SCEPTRE system.